Processing Payment Transactions Without a Secure Element

ABSTRACT

A user conducts a wireless payment transaction with a merchant system by transmitting payment information from a user device to a terminal reader without accessing a secure element resident on the user device. A user taps a user device in a merchant system&#39;s terminal reader&#39;s radio frequency field. The terminal reader and the user device establish a communication channel and the terminal reader transmits a signal comprising a request for a payment processing response. The signal is received by the user device and converted by a controller to a request understandable by an application host processor. The controller transmits the request to the application host processor, where the request is processed, and a response is transmitted to the controller and then to the terminal reader. The response generated by the application host processor is identifiable by the merchant system as a payment response.

RELATED APPLICATION

This patent application claims priority under 35 U.S.C. § 119 to U.S.Patent Application No. 61/635,277, filed Apr. 18, 2012 and entitled“Processing a Contactless Payment Transaction Without a Secure Element.”The entire contents of the above-identified application is hereby fullyincorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to a payment transaction, andmore particularly to a payment transaction made via a user computingdevice without accessing a secure element of the user device.

BACKGROUND

Current near field communication (“NFC”) systems rely on a hardwarecomponent commonly referred to as a “secure element” installed oncommunication devices to provide a secure operating environment forfinancial transactions, transit ticketing, identification andauthentication, physical security access, and other functions. A secureelement generally includes its own operating environment with atamper-proof microprocessor, memory, and operating system. An NFCcontroller receives a payment request message from a merchant's point ofsale (“POS”) system and transmits the message to the secure element forprocessing. A typical NFC controller comprises the secure element. Atrusted service manager (“TSM”), or other form of secure serviceprovider, can, among other things, install, provision, and personalizeapplications and data in the secure element. The secure element has oneor more access keys that are typically installed at manufacture time. Acorresponding key is shared by the TSM so that the TSM can establish acryptographically secure channel to the secure element for installation,provisioning, and personalization of the secure element while the devicehaving the secure element is in the possession of an end user. In thisway, the secure element can remain secure even if the host CPU in thedevice has been compromised.

One deficiency with current NFC systems is that a tight coupling existsbetween the secure element and the TSM. For current deployments, onlyone TSM has access to the keys of a particular secure element.Therefore, the end user can choose to provision secure element featuresthat are supplied by the one TSM only. The manufacturer of the devicetypically chooses this TSM. For example, a smart phone manufacturer mayselect the TSM for smart phones under guidance from a mobile networkoperator (“MNO”), such as Sprint or Verizon, that purchases the smartphone rather than the end user. Thus, the TSM features available to theend user may not be in the end user's interest. As an example, the MNOmay have a business relationship with only one payment provider, such asMasterCard or Bank of America. That TSM may allow the secure element tobe provisioned with payment instructions from the one payment provideronly. Thus, the end user would not be able to access services from otherpayment providers, such as VISA.

SUMMARY

In certain example aspects described herein, a method for processing apayment transaction without accessing the secure element comprises aterminal reader that facilitates a communication channel with a userdevice. A user taps the user device in the terminal reader's radiofrequency field. The terminal reader and the user device establish acommunication channel, and the terminal reader transmits a signalcomprising a request for a payment processing response. The signal isreceived by the user device and converted by a controller to a requestunderstandable by the application host processor. The controllertransmits the request to the application host processor, where therequest is processed and a response is transmitted to the controller andthen to the terminal reader. The response generated by the applicationhost processor is identifiable by the merchant system as a paymentresponse and is indistinguishable from, or provides the samefunctionality as, a response generated by a conventional secure element.

These and other aspects, objects, features, and advantages of theexample embodiments will become apparent to those having ordinary skillin the art upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a payment processing system, inaccordance with example embodiments.

FIG. 2 is a block flow diagram depicting a method for processing apayment without accessing the secure element, in accordance with exampleembodiments.

FIG. 3 is a block flow diagram depicting a method for processing apayment processing response, in accordance with example embodiments.

FIG. 4 is a block flow diagram depicting a method for processing arequest for payment information, in accordance with example embodiments.

FIG. 5 is a block flow diagram depicting a method for processing apayment, in accordance with example embodiments.

FIG. 6 is a block diagram depicting a computer machine and module, inaccordance with certain example embodiments.

DETAILED DESCRIPTION OF THE EXAMPLE EMBODIMENTS Overview

The example embodiments described herein provide methods and systemsthat enable processing of a payment transaction without accessing asecure element of a user device. In an example embodiment, the user isconducting a wireless payment transaction with a merchant system bytransmitting payment information from the user device to a terminalreader. The secure element resident on the user device may be tightlycoupled to a TSM at the time of manufacturer, thereby preventing theuser from providing payment instructions for a payment account notprovisioned on the secure element. In an example embodiment, the userdevice comprises an application host processor capable of transmittingpayment information without accessing the secure element.

A user taps the user device in the terminal reader's radio frequencyfield. The terminal reader and the user device establish a communicationchannel and the terminal reader transmits a signal comprising a requestfor a payment processing response. The signal is received by the userdevice and converted by the controller to a request understandable bythe application host processor. The controller transmits the request tothe application host processor, where the request is processed and aresponse is generated. The response generated by the application hostprocessor is identifiable by the merchant system as a payment responseand is indistinguishable from a response generated by the secureelement. The response is transmitted by the application host processorto the controller, where it is converted into a signal for transmissionto the terminal reader. The signal is transmitted to the terminal readerwhere it is received and transmitted to the merchant system. Anapplication resident on the merchant system processes the signal andconverts it to a response understandable by the merchant system. Themerchant system reads the response, which comprises an affirmativeindication that the user device can proceed with the paymenttransaction.

The merchant system generates a request for payment information andtransmits the request to the terminal reader. The terminal readertransmits the request in the form of a signal transmittable via thecommunication channel established between the terminal reader and theuser device. The signal is received by the user device and converted bythe controller to a request understandable by the application hostprocessor. The controller transmits the request to the application hostprocessor, where the request is processed and a response is generated.The response comprises a payment account number to use for thetransaction. The payment account number may comprise a number associatedwith a financial account associated with the user, for example, a creditaccount number, debit account number, stored value account number, giftcard account number, coupon, loyalty account number, reward accountnumber, or bank account number. The response may also or insteadcomprise a proxy account number generated by an account managementsystem or the application host processor. The proxy account numbercomprises information that routes the payment transaction to the accountmanagement system where the user's actual financial account informationcan be retrieved. The proxy account numbers may have time, geographicand/or value limitations. The proxy account numbers may also havelimitations on the number of times they may be used.

The response, which comprises the payment account information, istransmitted by the application host processor to the controller, whereit is converted into a signal for transmission to the terminal reader.The signal is transmitted to the terminal reader where it is receivedand transmitted to the merchant system. An application resident on themerchant system processes the signal and converts it to a responseunderstandable by the merchant system. The merchant system reads thepayment account information and processes the payment.

The inventive functionality of the invention will be explained in moredetail in the following description, read in conjunction with thefigures illustrating the program flow.

Example System Architectures

Turning now to the drawings, in which like numerals indicate like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a payment processing system, inaccordance with certain example embodiments. As depicted in FIG. 1 , theexample operating environment 100 comprises a merchant system 105, auser device system 120, an account management system 140, an acquirersystem 150, a card network system 160, and an issuer system 170 that areconfigured to communicate with one another via one or more networks 130.In some example embodiments, two or more of these systems (includingsystems 105, 120, 140, 150, 160, and 170) are integrated into the samesystem.

Each network 130 includes a wired or wireless telecommunication means bywhich network systems (including systems 105, 120, 140, 150, 160, and170) can communicate and exchange data. For example, each network 130can be implemented as, or may be a part of, a storage area network(SAN), personal area network (PAN), a metropolitan area network (MAN), alocal area network (LAN), a wide area network (WAN), a wireless localarea network (WLAN), a virtual private network (VPN), an intranet, anInternet, a mobile telephone network, a card network, Bluetooth, nearfield communication network (NFC), any form of standardized radiofrequency, or any combination thereof, or any other appropriatearchitecture or system that facilitates the communication of signals,data, and/or messages (generally referred to as data). Throughout thisspecification, it should be understood that the terms “data” and“information” are used interchangeably herein to refer to text, images,audio, video, or any other form of information that can exist in acomputer-based environment.

In an example embodiment, NFC communication protocols include, but arenot limited to ISO/IEC 14443 type A and/or B technology (hereafter “ISO14443”), MIFARE technology (hereafter “MIFARE”), and/or ISO/IEC 18092technology (hereafter “ISO 18092”). ISO 14443 is a communicationprotocol for user devices operating in close proximity with a reader. AnISO 14443 communication protocol is utilized for secure card payments,including but not limited to credit card payments, debit card payments,and other forms of financial card payments. MIFARE is a communicationprotocol for user devices that comply with proprietary device standardsthat are based on ISO 14443. A MIFARE protocol is utilized for storedfunction transactions, including but not limited to gift cards, transitcards, tickets, access cards, loyalty cards, and other forms of storedvalue card transactions. A MIFARE protocol may also be used for limitedvalue-added services. ISO 18092 is a communication protocol for userdevices operating at higher bit rates, allowing for richer communicationbetween the devices. An ISO 18092 communication protocol is utilized forpeer-to-peer communication, value-added services (including, but notlimited to, coupons, loyalty cards, check-ins, membership cards, giftcards, and other forms of value-added services), and other forms ofricher communication. Any suitable NFC communication protocol can beused for NFC communication between the user device 120 and the terminalreader 115 to implement the methods and functionality described herein.

In an example embodiment, each network system (including systems 105,120, 140, 150, 160, and 170) comprises a device having a communicationmodule capable of transmitting and receiving data over the network 130.For example, each network system (including systems 105, 120, 140, 150,160, and 170) may comprise a server, personal computer, mobile device(for example, notebook computer, tablet computer, netbook computer,personal digital assistant (PDA), video game device, GPS locator device,cellular telephone, Smartphone, or other mobile device), a televisionwith one or more processors embedded therein and/or coupled thereto, orother appropriate technology that includes or is coupled to a webbrowser or other application for communicating via the network 130. Inthe example embodiment depicted in FIG. 1 , the network systems(including systems 105, 120, 140, 150, 160, and 170) are operated bymerchants, users or consumers, an account management system operator,acquirer system operator, card network system operator, and issuersystem operator, respectively.

The merchant system 105 comprises at least one point of sale (“POS”)terminal 110 that is capable of processing a purchase transactioninitiated by a user. In an example embodiment, the merchant operates anonline store and the user indicates a desire to make a purchase byclicking a link or “checkout” button on a website. In some exampleembodiments, the user device 120 is configured to perform the functionsof the POS terminal 110. In this example, the user scans and/or pays forthe transaction via the user device 120 without interacting with the POSterminal 110. An example merchant system 105 comprises at least aterminal reader 115 that is capable of communicating with the userdevice system 120 and a merchant POS terminal 110 via an application118. The application 118 may be an integrated part of the POS terminal110 or merchant system 105 (not shown in FIG. 1 ), an integrated part ofthe terminal reader 115 (shown), or a standalone hardware device (notshown), in accordance with some example embodiments.

In an example embodiment, the terminal reader 115 is capable ofcommunicating with the user device 120 using an NFC communicationmethod. In another example embodiment, the terminal reader 115 iscapable of communicating with the user device 120 using a Bluetoothcommunication method. In yet another embodiment, the terminal reader 115is capable of communicating with the user device 120 using a Wi-Ficommunication method. In some example embodiments, the user scans a QRcode or bar code or clicks a URL link on the user device 120, whichtemporarily associates the user device 120 to the online merchant system105. The POS terminal 110 queries the online merchant system 105 to linkto the user and/or user device 120. In an example embodiment, theterminal reader 115 may be configured to read any number of barcodeformats, including without limitation, a QR code, a universal productcode (“UPC”), a global trade item number (“GTIN”), a stock keeping unit(“SKU”), a Japanese article number (“JAN”), a world product code(“WPC”), an International Standard Book Number (“ISBN”), a EuropeanArticle Number (“EAN”), etc. According to other example embodiments,terminal reader 115 may be an electronic field generator with a CPU, alaser scanner, a charged-coupled device (“CCD”) reader, a camera-basedreader, an omni-directional bar code scanner, a camera, a RFID reader,or any other device that is capable of reading product identifierinformation in a merchant system 105.

In an example embodiment, the user device 120 may be a personalcomputer, mobile device (for example, notebook, computer, tabletcomputer, netbook computer, personal digital assistant (“PDA”), videogame device, GPS locator device, cellular telephone, Smartphone or othermobile device), television with one or more processors embedded thereinand/or coupled thereto, or other appropriate technology that cancommunicate via an electronic, magnetic, or radio frequency fieldbetween the device 120 and another device, such as a terminal reader115. In an example embodiment, the user device 120 has processingcapabilities, such as storage capacity/memory and one or moreapplications (not illustrated) that can perform a particular function.In an example embodiment, the user device 120 contains an operatingsystem (not illustrated) and user interface 121. In some exampleembodiments, the user device 120 comprises an operating system (notillustrated) that communicates through an audio port or auxiliary dataport without a user interface 121.

The user device 120 also comprises a controller 125. In an exampleembodiment, the controller 125 is an NFC controller. In some exampleembodiments, the controller 125 is a Bluetooth link controller. TheBluetooth link controller may be capable of sending and receiving data,performing authentication and ciphering functions, and directing how theuser device 120 will listen for transmissions from the terminal reader115 or configure the user device 120 into various power-save modesaccording to the Bluetooth-specified procedures. In another exampleembodiment, the controller 125 is a Wi-Fi controller or an NFCcontroller capable of performing similar functions.

The user device 120 communicates with the terminal reader 115 via anantenna 127. In an example embodiment, once a user device applicationhas been activated and prioritized, the controller 125 is notified ofthe state of readiness of the user device 120 for a transaction. Thecontroller 125 outputs through the antenna 127 a radio signal, orlistens for radio signals from the device reader 115. On establishing asecure communication channel between the user device 120 and theterminal reader 115, the reader 115 requests a payment processingresponse from the user device 120.

An example controller 125 receives a radio wave communication signalfrom the terminal reader 115 transmitted through the antenna 127. Thecontroller 125 converts the signal to readable bytes. In an exampleembodiment, the bytes comprise digital information, such as a requestfor a payment processing response or a request for payment cardinformation. The controller 125 transmits the request to the applicationhost processor 123.

An example user device 120 may comprise a secure element or securememory (not shown), which can exist within a removable smart chip or asecure digital (“SD”) card or which can be embedded within a fixed chipon the device 120. In certain example embodiments, Subscriber IdentityModule (“SIM”) cards may be capable of hosting a secure element, forexample, an NFC SIM Card. The secure element (not shown) allows asoftware application resident on the user device 120 and accessible bythe device user to interact securely with certain functions within thesecure element, while protecting information stored within the secureelement (not shown). In an example embodiment, the secure element (notshown) comprises components typical of a smart card, such as cryptoprocessors and random generators. In an example embodiment, the secureelement (not shown) comprises a Smart MX type NFC controller in a highlysecure system on a chip controlled by a smart card operating system,such as a JavaCard Open Platform (“JCOP”) operating system. In anotherexample embodiment, the secure element (not shown) is configured toinclude a non-EMV type contactless smart card, as an optionalimplementation. The secure element (not shown) communicates with theapplication in the user device 120. In an example embodiment, the secureelement (not shown) is capable of storing encrypted user information andonly allowing trusted applications to access the stored information. Inan example embodiment, a controller 125 interacts with a secure keyencrypted application for decryption and installation in the secureelement.

In an example user device 120, a payment request is processed by theapplication host processor 123, instead of by a secure element (notshown). An example application host processor 123 can exist within aremovable smart chip or a secure digital (“SD”) card or which can beembedded within a fixed chip on the device 120. The application hostprocessor may comprise applications (not shown) running thereon thatperform the functionality described herein. In an example embodiment,the user device 120 communicates payment account information to themerchant system 105 in the form of a proxy or virtual accountidentifier, without transmitting the user's actual account information.The user's actual account information is maintained by the accountmanagement system 140 instead of within a secure element (not shown)resident on the user device 120.

An example merchant system 105 and user device 120 communicate with theaccount management system 140. The account management system 140 enablesthe storage of one or more payment accounts for the user. In an exampleembodiment, the user registers one or more payment accounts, forexample, credit card accounts, debit accounts, bank accounts, gift cardaccounts, coupons, stored value accounts, loyalty accounts, rewardsaccounts, and other forms of payment accounts capable of making apurchase with the account management system 140. For example, the usermay create a digital wallet account with the account management system140. The payment accounts may be associated with the user's digitalwallet account maintained by the account management system 140. The usermay access the digital wallet account at any time to add, change orremove payment accounts. In an example embodiment, the user's digitalwallet information is transmitted to the user's user device 120,enabling use of the user's payment account without accessing the accountmanagement system 140. In some example embodiments, the accountmanagement system 140 transmits limited-use proxy account information tothe user device 120 enabling use of the payment accounts during apayment transaction routed to the account management system 140 duringthe payment processing. For example, the proxy account number may routethe payment authorization request to the account management system 140,acting as the issuer system 170 for the proxy account. In anotherexample embodiment, the user device 120 may comprise an application (notshown) that generates limited use proxy account numbers that are enablethe payment transaction to be routed to the account management system140. In some example embodiments, the application host processor 123performs this function.

An example account management system 140 comprises a data storage unit145 accessible by the account management system 140. The example datastorage unit 145 can include one or more tangible computer-readablestorage devices capable of storing a user's payment account information.The user may request a purchase from the merchant system 105. In anexample embodiment, the purchase is initiated by a wireless “tap” of theuser device 120 with the terminal reader 115. The merchant system 105interacts with the acquirer system 150 (for example Chase, PaymentTech,or other third party payment processing companies), the card networksystem 160 (for example VISA, MasterCard, American Express, Discover, orother card processing networks), and the issuer system 170 (for exampleCitibank, CapitalOne, Bank of America, and other financial institutionsto authorize payment) to process the payment. In some exampleembodiments, the payment card information transmitted by the user device120 to the terminal reader 115 is a proxy account number or a tokenaccount number that links the payment transaction to a user accountmaintained by the account management system 140. The payment transactionis routed to the account management system 140 for identification of theuser's correct payment card information.

The components of the example-operating environment 100 are describedhereinafter with reference to the example methods illustrated in FIGS.2-5 . The example methods of FIG. 2-5 may also be performed with othersystems and in other environments.

Example System Processes

FIG. 2 is a block flow diagram depicting a method for processing apayment without accessing the secure element, in accordance with exampleembodiments. The method 200 is described with reference to thecomponents illustrated in FIG. 1 .

In block 205, the user taps the user device 120 in the proximity of theterminal reader 115. In an example embodiment, the terminal reader 115generates a radio frequency (“RF”) or other field polling for thepresence of a user device 120, and the user “taps” the user device 120by placing the device 120 within the field of the terminal reader 115.In some example embodiments, the merchant activates the RF field orother field to poll for the presence of a user device 120 using anapplication 118 on the terminal reader 115. In certain exampleembodiments, the systems and methods described in FIGS. 2-5 herein areperformed while the user device 120 is tapped.

In block 210, the user device 120 and the terminal reader 115 establisha communication channel. In an example embodiment, the communicationchannel is an NFC communication channel. In some example embodiments,the communication channel is a Bluetooth communication channel. In yetanother example embodiment, the communication channel is a Wi-Ficommunication channel. Accordingly, the payment transaction can beconducted via wireless or “contactless” communication between the userdevice 120 and the terminal reader 115.

In an example embodiment, the terminal reader 115 requests protocols andcharacteristics from the user device 120 to establish the communicationchannel. For example, the terminal reader 115 may request theidentification of communication protocols (for instance ISO/IEC 14443,MIFARE, and/or ISO/IEC 18092), a list of applications available, andsecurity protocols from the user device 120.

In block 215, the terminal reader 115 transmits a signal requesting apayment processing response to the user device 120. In an exampleembodiment, the payment process response is a request to proceed with afinancial payment transaction. In an example embodiment, the paymentprocess response indicates to the terminal reader 115 that the userdevice 120 is capable of performing a financial transaction. In atypical wireless payment transaction involving a secure element, theuser device 120 responds to the terminal reader's 115 request with amessage created by the secure element. This message is understandable bythe terminal reader 115 to comprise a payment process response. In anexample embodiment, a payment process response is created by theapplication host processor 123 resident in the user device 120, not thesecure element. The payment process response is understandable by theterminal reader 115 in the same manner as a response created by thesecure element.

In block 220, the user device 120 receives the signal transmitted by theterminal reader 115. In an example embodiment, the signal is received bythe antenna 127 and transmitted to the controller 125. In an exampleembodiment, the tap is an NFC tap and the controller 125 is an NFCcontroller.

In block 225, the controller 125 converts the signal into a readablerequest for the payment processing response. In an example embodiment,signal is converted into bytes comprising the readable request for thepayment processing response.

In block 230, the controller 125 transmits the request for the paymentprocessing response to the application host processor 123. In an exampleembodiment, the application host processor 123 functions in a mannersimilar to a secure element during the payment transaction.

In block 235, the request for the payment processing response isprocessed. The method for processing the request for the paymentprocessing response is described in more detail hereinafter withreference to the methods described in FIG. 3 .

FIG. 3 is a block flow diagram depicting a method for processing apayment processing response, in accordance with example embodiments, asreferenced in block 235 of FIG. 2 . The method 235 is described withreference to the components illustrated in FIG. 1 .

In block 310, the application host processor 123 receives the requestfor the payment processing response. In an example embodiment, therequest is transmitted through a series of connections before beingreceived by the application host processor 123. In some exampleembodiments, the request is transmitted directly from the controller 125to the application host processor 123.

In block 320, the application host processor 123 generates the paymentprocessing response. In an example embodiment, the payment processingresponse comprises language understandable by the terminal reader 115indicating that the user device 120 is capable of completing a paymenttransaction. In an example embodiment, the payment processing responsecomprises the same language and/or information as a payment processingresponse generated by a conventional secure element or secure memory. Inan example embodiment, the payment processing response comprises useridentifiable data, personal identifiers, account identifiers, paymentnetwork configuration data, merchant specific data, and/or securitydata, any of which may used to validate the sequence of transactionsperformed on a user's account.

In block 330, the application host processor 123 transmits the paymentprocessing response to the controller 125. In an example embodiment,payment processing response is transmitted through a series ofconnections before being received by the controller 125. In some exampleembodiments, the payment processing response is transmitted directly tothe controller 125.

In block 340, the controller 125 receives the payment processingresponse. In an example embodiment, the payment processing responsecomprises bytes that will be converted by the controller 125 into atransmittable signal.

In block 350, the controller 125 transmits the payment processingresponse to the terminal reader 115. In an example embodiment, thepayment processing response is a signal transmitted by the antenna 127to the terminal reader 115.

In block 360, the terminal reader 115 receives the payment processingresponse. In an example embodiment, the terminal reader 115 receives thesignal transmitted by the user device.

In block 370, the terminal reader transmits the payment processingresponse to the merchant system 105. In an example embodiment, thepayment processing response is transmitted to the POS terminal 110resident in the merchant system 105.

In block 380, the merchant system 105 receives the payment processingresponse. In an example embodiment, the application 118 resident on themerchant system converts the signal into a language understandable bythe merchant system 105. In an example embodiment, the merchant system105 understands the payment processing response to comprise anaffirmative response that the user device 120 is capable of performingthe payment transaction.

The method 235 then proceeds to block 240 in FIG. 2 .

Returning to FIG. 2 , in block 240, a request for payment accountinformation is processed. The method for processing the payment accountinformation is described in more detail hereinafter with reference tothe methods described in FIG. 4 .

FIG. 4 is a block flow diagram depicting a method for processing arequest for payment information, in accordance with example embodiments,as referenced in block 240 of FIG. 2 . The method 240 is described withreference to the components illustrated in FIG. 1 .

In block 410, the merchant system 105 generates and transmits a requestfor payment account information to the terminal reader 115. In anexample embodiment, the request for a payment processing responsecomprises a request for payment account information and the methodsdescribed in blocks 410 through 490 and in block 240 through 265 are notrequired.

In block 420, the terminal reader 115 receives the request for paymentaccount information transmitted by the merchant system 105. In anexample embodiment, the application 118 resident on the merchant system105 reads the payment processing response and generates a request forpayment account information in response. In an example embodiment, therequest is converted to a signal capable of being transmitted to theuser device 120 via the communication channel and converted into bytesunderstandable by the application host processor 123.

In block 430, the terminal reader 115 transmits a signal comprising therequest for payment account information to the user device 120. In anexample embodiment, the request for payment account informationcomprises a request for information to complete a payment transaction,such as the account number, the expiration date, and the security code.

In block 440, the user device 120 receives the signal transmitted by theterminal reader 115. In an example embodiment, the signal is received bythe antenna 127 and transmitted to the controller 125.

In block 450, the controller 125 converts the signal into a readablerequest for the payment account information. In an example embodiment,signal is converted into bytes comprising the readable request for thepayment account information.

In block 460, the controller 125 transmits the request for the paymentaccount information to the application host processor 123. In an exampleembodiment, the application host processor 123 functions in a mannersimilar to a secure element during the payment transaction.

In block 470, the application host processor 123 receives the requestfor the payment account information. In an example embodiment, therequest is transmitted through a series of connections before beingreceived by the application host processor 123. In some exampleembodiments, the request is transmitted directly from the controller 125to the application host processor 123.

In block 480, the application host processor 123 generates the paymentaccount information to be used for the payment transaction. In anexample embodiment, the user registers one or more payment accounts, forexample, credit card accounts, debit accounts, bank accounts, gift cardaccounts, coupons, stored value accounts, loyalty accounts, rewardsaccounts, and other forms of payment accounts capable of making apurchase with the account management system 140. For example, the usermay create a digital wallet account with the account management system140, which associates the payment accounts with the user and/or theuser's user device 120. The digital wallet account information can bestored in the account management system 140 and also may be storedlocally in the user's user device 120.

In an example embodiment, the user's digital wallet information wastransmitted to the user's user device 120, and the application hostprocessor 123 generates the payment account information by accessing theuser's payment accounts saved in the user's digital wallet account. Inthis embodiment, the application host processor 123 can select aparticular payment account to use in the payment transaction.

In some example embodiments, the account management system 140 transmitsone or more limited use proxy account numbers to the user device 120.The application host processor 123 generates the payment accountinformation by accessing the transmitted limited use proxy accountnumbers and selecting a particular proxy account number to use for thetransaction. In an example embodiment, the account management system 140may periodically generate a limited use proxy account number and updatethe user's user device 120 with the current number. In some exampleembodiments, the user's user device 120 can communicate a request for alimited use proxy account number to the account management system 140,and the account management system 140 can, in response, communicate thelimited use proxy account number to the user's user device 120 for usein the payment transaction. In yet another example embodiment, theapplication host processor 123 generates the proxy account numberlocally. The application host processor 123 can communicate thegenerated limited use proxy account number to the account managementsystem 140 for verification by the account management system 140 whenthe account management system 140 receives the payment request from themerchant system 105. In some example embodiments, the application hostprocessor can generate the limited use proxy account number using ascheme that can be replicated by the account management system 140 toallow the account management system 140 to verify the generated limiteduse proxy account number when the account management system 140 receivesthe payment request from the merchant system 105.

The proxy account numbers may have time or geographic limitations. Forexample, the proxy account number may only be valid for a limited amountof time or it may only be valid in a specific geographic location. Thelimited use proxy account number can be stamped with, have encodedtherein, or otherwise contain a time reference, a time duration, ageographic position of the user device 120, and/or a geographic regionbased on a geographic position of the user device 120. These featurescan allow the limited use proxy account number to expire after aspecified period of time or when used outside of a specified geographiclocation. The proxy account numbers may also have limitations on thenumber of times they may be used. For example, each proxy account numbermay only be valid for a single use.

In block 490, the application host processor 123 transmits the paymentaccount information to the controller 125. In an example embodiment,payment account information is transmitted through a series ofconnections before being received by the controller 125. In some exampleembodiments, the payment processing response is transmitted directly tothe controller 125.

The method 240 then proceeds to block 245 in FIG. 2 .

Returning to FIG. 2 , in block 250, the controller 125 receives thepayment account information. In an example embodiment, the paymentaccount information comprises bytes that will be converted by thecontroller 125 into a transmittable signal.

In block 250, the controller 125 transmits the payment accountinformation to the terminal reader 115. In an example embodiment, thepayment account information is a signal transmitted by the antenna 127to the terminal reader 115.

In block 255, the terminal reader 115 receives the payment accountinformation. In an example embodiment, the terminal reader 115 receivesthe signal transmitted by the user device 120.

In block 260, the terminal reader transmits the payment processingresponse to the merchant system 105. In an example embodiment, thepayment processing response is transmitted to the POS terminal 110resident in the merchant system 105.

In block 265, the merchant system 105 receives the payment accountinformation. In an example embodiment, the application 118 resident onthe merchant system 105 converts the signal into a languageunderstandable by the merchant system 105. In an example embodiment, theuser may be prompted to enter a personal identification number (“PIN”)into the merchant system 105.

In block 270, the payment is processed. The methods for processing thepayment are described in more detail hereinafter with reference to themethods described in FIG. 5 .

FIG. 5 is a block flow diagram depicting a method for processing apayment, in accordance with example embodiments, as referenced in block270 of FIG. 2 . The method 270 is described with reference to thecomponents illustrated in FIG. 1

In block 505, the merchant system 105 generates a payment requestmessage to request payment using the payment account informationprovided by the user device 120 and submits the payment request to theacquirer system 150. In an example embodiment, the merchant's POSterminal 110 submits the request to the acquirer system 150 via anetwork 130.

In block 510, the acquirer system 150 receives the payment request andsubmits it to the card network system 160.

In block 515, the card network system 160 determines whether the paymentaccount information used to pay for the transaction is a classic accountnumber. In an example embodiment, the card network system 160automatically makes this determination using a series of numbers orrouting information in the payment account information. In some exampleembodiments, the card network system 160 reviews a list of saved accountidentification information provided to the card network system 160 bythe account management system 140.

If the account number is a classic account number, the payment isprocessed according to traditional payment processing methods, in block520. In an example embodiment, the account number is a classic paymentaccount if it is capable of being routed to the issuer system withoutprocessing by the account management system 140 (for example, if theuser device 120 transmitted the user's actual credit card accountnumber, debit card account number, stored value account number, giftcard account number, or bank account number to the merchant system 105).

Returning to block 515, if the account number is not a classic accountnumber, the issuer system 170 is the account management system 140 (forexample, if the proxy account information was used for the transaction).The card network system 160 then forwards the payment request to theaccount management system 140, in block 525.

In some example embodiments, the payment account information cancomprise an identifier that corresponds to the list of saved accountidentification information, such as a block of account numbers or otherindicia, which identifies the issuer system 170 or the accountmanagement system 140. Based on this identifier, the payment isprocessed according to traditional payment processing methods, in block520, if the identifier corresponds to a conventional issuer system 170,or the payment is forwarded to the account management system 140, inblock 525, if the identifier corresponds to the account managementsystem 140.

In some example embodiments, the methods described in reference toblocks 515 and 525 may be performed by the acquirer system 150 or theissuer system 170, instead of the card network system 160.

In block 530, the account management system 140 receives the paymentrequest from the card network system 160.

In block 535, the account management system 140 identifies the userassociated with the proxy account information. In an example embodiment,account management system 140 contains a list of the proxy accountinformation generated for each user and can map this information to theuser's digital wallet account. some example embodiments, a one-wayalgorithm, such as a hash function, can be used to identify or associatethe user's digital wallet account with the proxy account information. Inyet another example embodiment, a hardware security module (“HSM”) canbe used to store secured data, such as a list of the proxy accountinformation generated for each user. The HSM can be contacted by theaccount management system 140 over a secure network to map the list ofproxy account information generated for each user to the user's digitalwallet account.

In an example embodiment, the account management system 140 verifiesthat the limitation rules for the proxy account information have notbeen violated. For example, the account management system 140 confirmsthat the proxy number has not violated a time/geographic limitation or alimitation on the number of uses.

In block 540, the account management system 140 identifies the user'ssaved payment account information. In an example embodiment, the user'sdigital wallet account contains the rules defined by the user (or thedefault rules if the user has not modified the default rules). If theuser has defined payment rules, the account management system 140applies the user-defined rules first to determine the order to apply thepayment accounts to the transaction. In an example embodiment, theaccount management system 140 applies the user-defined rules first.

In block 545, the account management system 140 generates and transmitsa new payment request to the issuer system 170 of the selected paymentaccount via the card network system 160. In some example embodiments,the account management system 140 is the issuer system 170 of thepayment account. In this embodiment, the account management system 140will determine whether sufficient funds are available for thetransaction and approve/deny the transaction accordingly.

In block 550, issuer 170 receives the new payment request from theaccount management system 140.

In block 555, the issuer 170 approves or declines the transaction. Ifthe transaction is declined, in block 557 the account management system140 is notified of the declined transaction. The account managementsystem 140 notifies the merchant system 105 of the declined transaction.

If the transaction is approved, the issuer system 170 transmits anauthorization message to the account management system 140 via the cardnetwork system 160, in block 560. If the account management system 140is the issuer system 170 of the payment account (see block 515), theaccount management system 140 notes the authorization of thetransaction.

In block 565, the account management system 140 receives theauthorization message and transmits an approval of the original paymentrequest to the card network system 160.

In block 570, the authorization message is transmitted to the merchantsystem 105 through the acquirer system 150.

In an example embodiment, the communication channel between the terminalreader 115 and the user device 120 is then terminated. In an exampleembodiment, the original communication channel can be terminated whenthe request to terminate a communication channel between the terminalreader 115 and the user device 120 is communicated, or any suitable timethereafter.

Other Example Embodiments

FIG. 6 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, aSmartphone, a set-top box, a kiosk, a vehicular information system, onemore processors associated with a television, a customized machine, anyother hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured tofunction using multiple computing machines interconnected via a datanetwork or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (“DSP”), an application specific integratedcircuit (“ASIC”), a graphics processing unit (“GPU”), a fieldprogrammable gate array (“FPGA”), a programmable logic device (“PLD”), acontroller, a state machine, gated logic, discrete hardware components,any other processing unit, or any combination or multiplicity thereof.The processor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain embodiments, the processor 2010 along with othercomponents of the computing machine 2000 may be a virtualized computingmachine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), flash memory, or anyother device capable of storing program instructions or data with orwithout applied power. The system memory 2030 may also include volatilememories such as random access memory (“RAM”), static random accessmemory (“SRAM”), dynamic random access memory (“DRAM”), and synchronousdynamic random access memory (“SDRAM”). Other types of RAM also may beused to implement the system memory 2030. The system memory 2030 may beimplemented using a single memory module or multiple memory modules.While the system memory 2030 is depicted as being part of the computingmachine 2000, one skilled in the art will recognize that the systemmemory 2030 may be separate from the computing machine 2000 withoutdeparting from the scope of the subject technology. It should also beappreciated that the system memory 2030 may include, or operate inconjunction with, a non-volatile storage device such as the storagemedia 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid state drive (“SSD”), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (“I/O”) interface 2060 may be configured to couple toone or more external devices, to receive data from the one or moreexternal devices, and to send data to the one or more external devices.Such external devices along with the various internal devices may alsobe known as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel,peripheral component interconnect (“PCP”), PCI express (PCIe), serialbus, parallel bus, advanced technology attached (“ATA”), serial ATA(“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, variousvideo buses, and the like. The I/O interface 2060 may be configured toimplement only one interface or bus technology. Alternatively, the I/Ointerface 2060 may be configured to implement multiple interfaces or bustechnologies. The I/O interface 2060 may be configured as part of, allof, or to operate in conjunction with, the system bus 2020. The I/Ointerface 2060 may include one or more buffers for bufferingtransmissions between one or more external devices, internal devices,the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, biometricreaders, electronic digitizers, sensors, receivers, touchpads,trackballs, cameras, microphones, keyboards, any other pointing devices,or any combinations thereof. The I/O interface 2060 may couple thecomputing machine 2000 to various output devices including videodisplays, speakers, printers, projectors, tactile feedback devices,automation control, robotic components, actuators, motors, fans,solenoids, valves, pumps, transmitters, signal emitters, lights, and soforth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to some embodiments, any of the processor 2010, theother elements of the computing machine 2000, or the various peripheralsdiscussed herein may be integrated into a single device such as a systemon chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with a opportunity to control whether programs orfeatures collect user information (e.g., information about a user'ssocial network, social actions or activities, profession, a user'spreferences, or a user's current location), or to control whether and/orhow to receive content from the content server that may be more relevantto the user. In addition, certain data may be treated in one or moreways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed herein. The systems, methods, and procedures described hereincan be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the invention claimedherein.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

1-20. (canceled)
 21. A computer-implemented method to process paymenttransactions without accessing secure memories, comprising: receiving,by a mobile computing device and from a merchant system computingdevice, a request for a payment processing response; converting, by themobile computing device, the request for the payment processing responseto a request readable by a non-secure memory processor of the mobilecomputing device; generating, by the non-secure memory processor of themobile computing device, a response to the request for the paymentprocessing response that is identifiable by the merchant system as apayment response generated by a secure memory processor; andtransmitting, by the mobile computing device, the response to therequest for the payment processing response to the merchant systemcomputing device.
 22. The computer-implemented method of claim 21,wherein the request for the payment processing response is a request toproceed with a financial payment transaction.
 23. Thecomputer-implemented method of claim 21, wherein the response to therequest for the payment processing response includes an indication thatthe mobile computing device is capable of performing a financialtransaction.
 24. The computer-implemented method of claim 21, whereinthe request for the payment processing response is a request for paymentaccount information.
 25. The computer-implemented method of claim 21,wherein the response to the request for the payment account informationcomprises a payment account identifier.
 26. The computer-implementedmethod of claim 25, wherein the payment account identifier is associatedwith at least one of a credit card account, a debit account, a storedvalue account, a gift card account, or a bank account for a userassociated with the mobile computing device.
 27. Thecomputer-implemented method of claim 26, wherein the payment accountidentifier is generated by an account management system and transmittedto the mobile computing device, wherein the account management systemmaintains information for at least one of the credit card account, thedebit account, the stored value account, the gift card account, or thebank account for the user associated with the mobile computing device.28. The computer-implemented method of claim 25, wherein the paymentaccount identifier is associated with at least one of a geographiclimitation, a time limitation, or a number of use limitation.
 29. Thecomputer-implemented method of claim 25, wherein the payment accountidentifier is retrieved from a digital wallet application on the mobilecomputing device.
 31. The computer-implemented method of claim 25,further comprising communicating, by the mobile computing device, thepayment account identifier to an account management system for paymentaccount identifier verification during processing of a payment request.32. The computer-implemented method of claim 25, wherein the non-securememory processor resident on the mobile computing device generates thepayment account identifier using a scheme that can be replicated by anaccount management system during processing of a payment request. 33.The computer-implemented method of claim 21, wherein the response to therequest for the payment processing response includes at least one of aproxy account number or a token account number.
 34. Thecomputer-implemented method of claim 21, wherein converting the requestfor the payment processing response to the request readable by thenon-secure memory processor comprises: converting the request for thepayment processing response to a readable request for a paymentprocessing response by the non-secure memory processor of the mobilecomputing device.
 35. The computer-implemented method of claim 21,wherein converting, by the mobile computing device, the request for thepayment processing response to the request readable by the non-securememory processor comprises converting the request for the paymentprocessing response into bytes comprising the request readable by thenon-secure memory processor.
 36. The computer-implemented method ofclaim 21, wherein the request for the payment processing responseprovides a same functionality as a response created by the secure memoryprocessor.
 37. The computer-implemented method of claim 21, wherein therequest for the payment processing response is indistinguishable from aresponse created by the secure memory processor.
 38. Thecomputer-implemented method of claim 21, wherein the request for thepayment processing response is received using a near field communication(NFC) protocol.
 39. The computer-implemented method of claim 21,wherein: generating, by the non-secure memory processor of the mobilecomputing device, the response to the request for the payment processingresponse comprises allowing the mobile computing device to processpayment transactions using financial account information for any of aplurality of payment providers without transferring control of a securememory processor from one payment provider to a different paymentprovider.
 40. One or more non-transitory computer-readable media havingcomputer-readable program instructions embodied thereon that whenexecuted by a mobile computing device cause the mobile computing deviceto perform operations, the operations comprising: receiving, by a mobilecomputing device and from a merchant system computing device, a requestfor a payment processing response; converting, by the mobile computingdevice, the request for the payment processing response to a requestreadable by a non-secure memory processor of the mobile computingdevice; and generating, by the non-secure memory processor of the mobilecomputing device, a response to the request for the payment processingresponse that is identifiable by the merchant system as a paymentresponse generated by a secure memory processor.
 41. The one or morenon-transitory computer-readable media of claim 40, wherein: the requestfor the payment processing response is a request to proceed with afinancial payment transaction; and the response to the request for thepayment processing response includes an indication that the mobilecomputing device is capable of performing a financial transaction. 42.The one or more non-transitory computer-readable media of claim 40,wherein: the request for the payment processing response is a requestfor payment account information; and the response to the request for thepayment account information comprises a payment account identifier. 43.The computer-implemented method of claim 42, wherein the payment accountidentifier is generated by an account management system and transmittedto the mobile computing device, wherein the account management systemmaintains information for at least one of the credit card account, thedebit account, the stored value account, the gift card account, or thebank account for the user associated with the mobile computing device.44. A mobile computing device for processing payment transactions,comprising: one or more storage devices; a controller communicativelycoupled to the one or more storage devices; and a processorcommunicatively coupled to the one or more storage devices and thecontroller, the controller of the mobile computing device configured toexecute application code instructions that are stored in the one or morestorage devices to cause the mobile computing device to: receive arequest for a payment processing process from a merchant systemcomputing device; and convert the request for the payment processingresponse to a request readable by the processor; and the processor ofthe mobile computing device configured to execute application codeinstructions that are stored in the one or more storage devices to causethe mobile computing device to: generate a response to the request forthe payment processing response that is identifiable as a responsegenerated by a secure element processor.
 45. The mobile computing deviceof claim 44, wherein: the request for the payment processing response isa request to proceed with a financial payment transaction; and theresponse to the request for the payment processing response includes anindication that the mobile computing device is capable of performing afinancial transaction.
 46. The mobile computing device of claim 44,wherein: the request for the payment processing response is a requestfor payment account information; the response to the request for thepayment account information comprises a payment account identifier; andthe payment account identifier is generated by the processor.
 47. Themobile computing device of claim 44, wherein the one or more storagedevices comprises a secure memory other than a secure element memory.48. The mobile computing device of claim 44, wherein the one or morestorage devices comprises a combination memory with secure memory andnon-secure memory portions.